Adding Cloud Devices for Monitoring
Overview
In order to get started with the monitoring for cloud devices, we need to first add the devices to Motadata AIOps and in turn enable it to collect data from these devices for monitoring. This guide helps you with the process of adding cloud devices to Motadata AIOps so that you are able to start monitoring them.
At a high level, this process includes creating a credential profile and a discovery profile, assigning the credential profile to a discovery profile, and executing a successful discovery run.
This is followed by provisioning the discovered devices as monitors in the system. This will enable Motadata AIOps to continuously monitor the resources and generate alerts and insights based on their performance metrics. You can also customize the monitoring settings for each monitor, such as the polling interval, threshold values, and alert notifications.
Motadata AIOps will collect performance data from the cloud resources and populate them in the system for further analysis.
Cloud Vendors and their Services Supported for Monitoring
You can add devices to AIOps to monitor them from all the major cloud vendors which include the following:
Amazon Web Services(AWS)
The services supported for monitoring for AWS:
| Supported Service |
|---|
| Amazon CloudFront |
| Amazon DocumentDB |
| Amazon DynamoDB |
| Amazon EBS |
| Amazon EC2 |
| Amazon RDS |
| Amazon S3 |
| Amazon SNS |
| Amazon SQS |
| Amazon ELB |
| AWS Lambda |
| AWS Elastic Beanstalk |
| AWS Auto Scaling |
Microsoft Azure
The services supported for monitoring for Microsoft Azure:
| Supported Service |
|---|
| Web App Service |
| Azure Storage |
| Azure VMs |
| Azure SQL Database |
| Azure Cosmos DB |
| Azure Application Gateway |
| Azure CDN |
| Azure Load Balancer |
| Virtual Machine Scale Sets |
| Azure Service Bus |
| Azure Functions |
Microsoft Office 365 Cloud(O365 Cloud)
The services supported for monitoring for O365:
| Supported Service |
|---|
| Microsoft Teams |
| Microsoft Sharepoint |
| Microsoft Exchange Online |
| Microsoft OneDrive |
Let us look into the process to add AWS, Azure, and O365 cloud to Motadata AIOps in detail.
- AWS
- Azure
- Office 365
Adding AWS resources for Monitoring
Prerequisites
- The Access Key and Secret Key of the AWS account are required.
- Your AWS user needs the following permissions assigned to IAM role to be successfully discovered using the Access Key and Secret Key. You can view the .JSON file with required permissions by clicking here.
1. Create a Credential Profile
We will start by creating a credential profile for the resource we are trying to add.
Navigation
Go to Menu. Select Settings 
. After that, Go to Discovery Settings 
and select Credential Profile. The credential profile screen is displayed. Select Create Credential Profile to create a new credential profile.
A pop-up for entering the credential profile details is displayed.
Credential Profile Parameters
Enter the required details in the pop-up as follows:
| Field | Description |
|---|---|
| Credential Profile Name | Provide a unique Credential Profile Name. This name is used to identify a credential profile. |
| Protocol | Select Cloud as Protocol from the drop-down.The option to provide the credential details is then displayed based on the protocol selected. |
| Cloud Type | Select AWS as the Cloud Type. |
| Access Key and Secret Key | Enter these details for the AWS account you want to monitor. |
Select Reset to erase all the current field values entered in the pop-up, if required.
Select Add Credential Profile to create the credential profile in the system. The credential profile is now created.
You can view the newly created profile on the credential profile screen by using the Search option available above the list of profiles.
Now, let's move to the next step and create a discovery profile.
2. Create a Discovery Profile
Let us create a discovery profile for the account we are trying to add. Discovery profile allows us to discover devices in a infrastructure using the device address and associated credential profile.
Navigation
Go to Menu. Select Settings . After that, Go to Network Discovery and select Discovery Profile. The discovery profile screen is displayed. Select Create Discovery Profile to create a new discovery profile.
A new screen to create the discovery profile is now displayed. Select Cloud from the menu as shown below.
AWS Cloud is selected by default.
Discovery Profile Parameters
Enter the required details in the screen as follows:
| Field | Description |
|---|---|
| Discovery Profile Name | Provide a unique Discovery Profile Name. This name is used to identify a discovery profile. |
| Collectors | Select one or more Collectors that should be used for collecting data from the devices discovered using this Discovery Profile. Select multiple Collectors for load balancing and failover mechanism. In case you don’t select a Collector, the AIOps shall automatically select a relevant collector to leverage the load balancing feature. |
Ensure that you select correct Collector(s) based on how you want to distribute the load across the collectors
| Groups | Select one or more Groups that will be assigned to the monitors you provision using this discovery profile. |
| Credential Profile | Select a created Credential Profile to assign it to the discovery profile you are trying to create. You can also create a new credential profile from this screen using the Create Credential Profile button. In this case, we will select the credential profile AWS_CLOUD_CRED we created in the 1st step while creating a credential profile. |
| Tags | Select one or more Tags that you wish to assign to the discovery profile. These tags will in turn be assigned to the device that you discover. |
| Discover Down Instances | Select ON or OFF for Discover Down Instances - If selected as ‘ON’, the system discovers the instances even if their services are down - If selected as ‘OFF’, the system doesn’t discover instances if their services are down. |
| Resources to be Monitored | - Select Monitor All Resources if you wish to monitor all the discovered resources using the discovery profile - Select Monitor Resources Selected By Tags if you wish to monitor specific resources based on the tags defined in the AWS environment. |
| Key/Value | This field is available when you select the Monitor Resources Selected By Tags in the previous option. Specify the Key and Value corresponding to the tags of the AWS resources that you wish to monitor. |
| Notify via E-mail and Notify via SMS | The system allows notifying users about a discovery run via E-mail and SMS: - Specify E-mail addresses (comma separated) in the Notify via E-mail field to trigger email notifications. - Specify mobile numbers (comma separated) in the Notify via SMS to send SMS notifications. |
Select Reset to erase all the current field values, if required.
Select Save and Exit if you wish to create the discovery profile but do do want to execute a discovery run currently.
Select Save and Run if you want execute the discovery run immediately after creation.
We have created a credential profile AWS_CLOUD_CRED in the 1st step. After that, we have created a discovery profile Aws_Cloud_Dis in the 2nd step and assigned the credential profile to the discovery profile. After selecting, Save and Run, we have initiated a discovery run which leads us to our next step, Provision the Discovered Devices as Monitors.
3. Provision the Discovered Devices as Monitors
After initiating the discovery profile execution, AIOps starts the process to discover the devices.
Once the discovery execution is complete, the list of all the devices discovered is displayed. Select the devices that you want to be listed as Monitors in the system.
Click on Add Selected Objects to add the selected devices as Monitors. These devices listed as Monitors will now be monitored further by AIOps.
These devices can be viewed under the Monitor tab from the Main Menu. Select the Monitor tab from the main menu. After that, Select Cloud to view all the monitors that are added to the system.
The AWS devices are now successfully added to AIOps.
Adding Azure resources for Monitoring
Prerequisites
- The Azure account needs to be integrated with Motadata AIOps with the help of Client ID, Tenant ID, and Secret Key of the Azure account. Refer this link to understand how to retrieve the above fields from the azure portal.
1. Create a Credential Profile
We will start by creating a credential profile for the device we are trying to add.
Navigation
Go to Menu. Select Settings . After that, Go to Network Discovery and select Credential Profile. The credential profile screen is displayed. Select Create Credential Profile to create a new credential profile.
A pop-up for entering the credential profile details is displayed.
Credential Profile Parameters
Enter the required details in the pop-up as follows:
| Field | Description |
|---|---|
| Credential Profile Name | Provide a unique Credential Profile Name. This name is used to identify a credential profile. |
| Protocol | Select Cloud as Protocol from the drop-down. The option to provide the credential details is then displayed based on the protocol selected. |
| Cloud Type | Select Azure as the Cloud Type. |
| Client ID, Tenant ID, and the Secret Key | Enter these details for the cloud device you want to monitor. |
Select Reset to erase all the current field values entered in the pop-up, if required.
Select Add Credential Profile to create the credential profile in the system. The credential profile is now created.
You can view the newly created profile in the credential profile screen by using the Search option available above the list of profiles.
Now, let's move to the next step and create a discovery profile.
2. Create a Discovery Profile
Let us create a discovery profile for the device we are trying to add. Discovery profile allows us to discover devices in an infrastructure using the device address and associated credential profile.
Navigation
Go to Menu. Select Settings . After that, Go to Network Discovery and select Discovery Profile. The discovery profile screen is displayed. Select Create Discovery Profile to create a new discovery profile.
A new screen to create the discovery profile is now displayed. Select Cloud from the menu as shown below.
AWS Cloud is selected by default. Select Azure Cloud to create a discovery profile for Azure.
Discovery Profile Parameters
Enter the required details in the screen as follows:
| Field | Description |
|---|---|
| Discovery Profile Name | Provide a unique Discovery Profile Name. This name is used to identify a discovery profile. |
| Collectors | Select one or more Collectors that should be used for collecting data from the devices discovered using this Discovery Profile. Select multiple Collectors for load balancing and failover mechanism. In case you don’t select a Collector, the AIOps shall automatically select a relevant collector to leverage the load balancing feature |
Ensure that you select correct Collector(s), based on how you want to distribute the load across all Collectors
| Groups | Select one or more Groups that will be assigned to the monitors you provision using this discovery profile. |
| Credential Profile | Select a created Credential Profile to assign it to the discovery profile you are trying to create. You can also create a new credential profile from this screen using the Create Credential Profile button. In this case, we will select the credential profile Azure_Cloud_Cred we created in the 1st step while creating a credential profile. |
| Tags | Select one or more Tags that you wish to assign to the discovery profile. These tags will in turn be assigned to the device that you discover. |
| Discover Down Instances | Select ON or OFF for Discover Down Instances - If selected as ‘ON’, the system discovers the instances even if their services are down. - If selected as ‘OFF’, the system doesn’t discover instances if their services are down. |
| Resources to be Monitored | - Select Monitor All Resources if you wish to monitor all the discovered resources using the discovery profile - Select Monitor Resources Selected By Tags if you wish to monitor specific resources based on the tags defined in the Azure environment. |
| Key/Value | This field is available when you select the Monitor Resources Selected By Tags in the previous option. Specify the Key and Value corresponding to the tags of the Azure resources that you wish to monitor. |
| Notify via E-mail and Notify via SMS | The system allows notifying users about a discovery run through E-mail and SMS - Specify E-mail addresses (comma separated) in the Notify via E-mail field to trigger email notifications. - Specify mobile numbers (comma separated) in the Notify via SMS to send SMS notifications. |
Select Reset to erase all the current field values, if required.
Select Save and Exit if you have created the discovery profile but do do want to execute a discovery run.
Select Save and Run if you want execute the discovery run immediately after creation.
We have created a credential profile Azure_Cloud_Cred in the 1st step. After that, we have created a discovery profile Azure_Cloud_Dis in the 2nd step and assigned the credential profile to the discovery profile. After selecting, Save and Run, we have inititated a discovery run which leads us to our next step, Provision the Discovered Devices as Monitors.
3. Provision the Discovered Devices as Monitors
After initiating the discovery profile execution, AIOps starts the process to discover the devices.
Once the discovery execution is complete, the list of all the devices discovered is displayed. Select the devices that you want to be listed as Monitors in the system.
Click on Add Selected Objects to add the selected devices as Monitors. These devices listed as Monitors will now be monitored further by AIOps.
These devices can be viewed under the Monitor tab from the Main Menu. Select the Monitor tab from the main menu. After that, Select Cloud to view all the monitors that are added to the system.
The Azure devices are now successfully added to AIOps.
Adding a Office 365 Cloud resource (O365)
Prerequisites
- The Client ID, Tenant ID, and the Secret Key of the O365 are required. Refer this link to understand how to retrieve the above fields from the O365 portal.
1. Create a Credential Profile
We will start by creating a credential profile for the device we are trying to add.
Navigation
Go to Menu. Select Settings . After that, Go to Network Discovery and select Credential Profile. The credential profile screen is displayed. Select Create Credential Profile to create a new credential profile.
A pop-up for entering the credential profile details is displayed.
Credential Profile Parameters
Enter the required details in the pop-up as follows:
| Field | Description |
|---|---|
| Credential Profile Name | Provide a unique Credential Profile Name. This name is used to identify a credential profile. |
| Protocol | Select Cloud as Protocol from the drop-down. The option to provide the credential details is then displayed based on the protocol selected. |
| Cloud Type | Select O365 as the Cloud Type. |
| Client ID, Tenant ID, and the Secret Key | Enter these details for the cloud resource you want to monitor. |
Select Reset to erase all the current field values entered in the pop-up, if required.
Select Add Credential Profile to create the credential profile in the system. The credential profile is now created.
You can view the newly created profile in the credential profile interface by using the Search option available above the list of profiles.
Now, let's move to the next step and create a discovery profile.
2. Create a Discovery Profile
Let us create a discovery profile for the device we are trying to add. Discovery profile allows us to discover devices in an infrastructure using the device address and associated credential profile.
Navigation
Go to Menu. Select Settings . After that, Go to Network Discovery and select Discovery Profile. The discovery profile screen is displayed. Select Create Discovery Profile to create a new discovery profile.
A new screen to create the discovery profile is now displayed. Select Cloud from the menu as shown below.
AWS Cloud is selected by default. Select Office 365 to create a discovery profile for a O365 device.
Discovery Profile Parameters
Enter the required details in the screen as follows:
| Field | Description |
|---|---|
| Discovery Profile Name | Provide a unique Discovery Profile Name. This name is used to identify a discovery profile. |
| Collectors | Select one or more Collectors that should be used for collecting data from the devices discovered using this Discovery Profile. Select multiple Collectors for load balancing and failover mechanism. In case you don’t select a Collector, the AIOps shall automatically select a relevant collector to leverage the load balancing feature. |
Ensure that you select correct Collector(s), based on how you want to distribute the load across all Collectors
| Groups | Select one or more Groups that will be assigned to the monitors you provision using this discovery profile. |
| Credential Profile | Select a created Credential Profile to assign it to the discovery profile you are trying to create. You can also create a new credential profile from this screen using the Create Credential Profile button. In this case, we will select the credential profile Office_365_Cred we created in the 1st step while creating a credential profile. |
| Tags | Select one or more Tags that you wish to assign to the discovery profile. These tags will in turn be assigned to the device that you discover. |
| Notify via E-mail and Notify via SMS | The system allows notifying users about a discovery run through e-mail and SMS - Specify email addresses (comma separated) in the Notify via E-mail field to trigger email notifications. - Specify mobile numbers (comma separated) in the Notify via SMS to send SMS notifications. |
Select Reset to erase all the current field values, if required.
Select Save and Exit if you have created the discovery profile but do do want to execute a discovery run.
Select Save and Run if you want execute the discovery run immediately after creation.
We have created a credential profile Office_365_Cred in the 1st step. After that, we have created a discovery profile Office_365_Dis in the 2nd step and assigned the credential profile to the discovery profile. After selecting, Save and Run, we have inititated a discovery run which leads us to our next step, Provision the Discovered Devices as Monitors.
3. Provision the Discovered Devices as Monitors
After initiating the discovery profile execution, AIOps starts the process to discover the devices.
Once the discovery execution is complete, the list of all the devices discovered is displayed. Select the devices that you want to be listed as Monitors in the system.
Click on Add Selected Objects to add the selected devices as Monitors. These devices listed as Monitors will now be monitored further by AIOps.
These devices can be viewed under the Monitor tab from the Main Menu. Select the Monitor tab from the main menu. After that, Select Cloud to view all the monitors that are added to the system.
The O365 devices are now successfully added to AIOps.